Standards - Mt Xia: Business Continuity/Disaster Recovery Methodologies

Additional documents of interest

Successful Business Continuity - Part 1 - Users and Groups
This article was published in the April 2005 issue of AIX Update magazine and discusses system administration needs and requirements oriented around users and groups. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters, such as user names, group names, UID and GID numbers.: This article was published in the April 2005 issue of AIX Update magazine and discusses system administration needs and requirements oriented around users and groups. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters, such as user names, group names, UID and GID numbers.
Successful Business Continuity - Part 2 - Machine and Host Names
This article was published in the May 2005 issue of AIX Update magazine and discusses naming structures for machines, systems, adapters, and aliases. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters.: This article was published in the May 2005 issue of AIX Update magazine and discusses naming structures for machines, systems, adapters, and aliases. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters.
Successful Business Continuity - Part 3 - Volume Names
This article was published in the December 2005 issue of AIX Update magazine and discusses naming structures for volume groups, logical volumes, log logical volumes, directory mount points, etc. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters.: This article was published in the December 2005 issue of AIX Update magazine and discusses naming structures for volume groups, logical volumes, log logical volumes, directory mount points, etc. The overall emphasis of this series of articles is for implementation of enterprise wide unique identifiers for a variety of parameters.
Successful Business Continuity - Part 4 - MQ Series, Startup/Shutdown Scripts, Error Processing
This article was published in the April 2006 issue of AIX Update magazine and discusses how to implement AIX in an environment dedicated to business continuity. The topic of this article is the assignment of MQ Series queue names and aliases, resource group startup and shutdown script names (Application startup/shutdown script names), error logging, and error notification.: This article was published in the April 2006 issue of AIX Update magazine and discusses how to implement AIX in an environment dedicated to business continuity. The topic of this article is the assignment of MQ Series queue names and aliases, resource group startup and shutdown script names (Application startup/shutdown script names), error logging, and error notification.
Successful Business Continuity - Part 5 - Miscellaneous topics
This article was published in the August 2006 issue of AIX Update magazine and discusses how to implement AIX in an environment dedicated to business continuity. A variety of topics is discussed in this article including automated documentation generation and management.: This article was published in the August 2006 issue of AIX Update magazine and discusses how to implement AIX in an environment dedicated to business continuity. A variety of topics is discussed in this article including automated documentation generation and management.
Automated Microcode Management System
One of the most difficult administration tasks in an AIX environment is attempting to keep the firmware and microcode up-to-date. Mt Xia has devised an automated method of gathering the Microcode information, determining which microcode needs to be updated, generating reports, and uploading the required microcode updates to each individual system.: One of the most difficult administration tasks in an AIX environment is attempting to keep the firmware and microcode up-to-date. Mt Xia has devised an automated method of gathering the Microcode information, determining which microcode needs to be updated, generating reports, and uploading the required microcode updates to each individual system.
Calculating the size of a Virtual Processor
This document describes the algorithms used to calculate the size of a virtual processor when using shared processors in an LPAR. The IBM documentation describes how to calculate CPU utilization, NOT how to size for configuration, this document clarifies this process. A description of the HMC input fields for the processor tab is included.: This document describes the algorithms used to calculate the size of a virtual processor when using shared processors in an LPAR. The IBM documentation describes how to calculate CPU utilization, NOT how to size for configuration, this document clarifies this process. A description of the HMC input fields for the processor tab is included.
Basics of Partition Load Manager Setup
This presentation was provided by Ron Barker from IBM regarding the PLM Basic setup.
ppt

pdf: This presentation was provided by Ron Barker from IBM regarding the PLM Basic setup.
ppt

pdf

HMC Standards

Contained here are the standards for defining new LPAR's in the Power5 architecture environment using the Hardware Management Console. These standards describe the information required to define the LPAR's and the format in which this information should be presented.

This environment utilizes the VIO server to virtualize the hardware I/O adapters to client LPAR's, thus allowing multiple LPAR's to share resources. Implementation of this type of environment requires extensive up-front design work and planning. Each hardware adapter must be identified to the VIO server and virtualized for use by each client LPAR.

To begin configuring this environment, build a spreadsheet to contain all frame and I/O adapter information, this spreadsheet should contain at least the following:

Frame Type:

Frame S/N:

System Name:

CPUs

RAM (GB)

CUoD CPUs

CUoD RAM (GB)

Drawer Serial Bus Slot Adapter LPAR

Much of this information can be automatically generated using the script "hmcparse.ksh". Example results from this script follow:

Server9119590SN51A432B

Drawer Serial Bus Slot Adapter LPAR

U5791.001.91800WT-P1 13 T6 SCSI bus controller dalapvio01

U5791.001.91800WT-P1 13 C08 Fibre Channel Serial Bus dalpocdb01

U5791.001.91800WT-P1 13 C09 Empty slot

U5791.001.91800WT-P1 13 C10 Empty slot

U5791.001.91800WT-P1 14 C01 PCI 1Gbps Ethernet dalapvio01

U5791.001.91800WT-P1 14 C02 PCI 10/100Mbps Ethernet w/ IPSec dalapvio02

U5791.001.91800WT-P1 14 C03 PCI 10/100Mbps Ethernet w/ IPSec dalapvio01

U5791.001.91800WT-P1 14 C04 PCI 10/100Mbps Ethernet w/ IPSec dalapvio02

U5791.001.91800WT-P1 15 T5 SCSI bus controller dalapvio01

U5791.001.91800WT-P1 15 C05 PCI 1Gbps Ethernet dalapvio01

U5791.001.91800WT-P1 15 C06 Fibre Channel Serial Bus dalapvio01

U5791.001.91800WT-P1 15 C07 Empty slot

U5791.001.91800WT-P2 19 T6 SCSI bus controller dalapvio01

U5791.001.91800WT-P2 19 C08 Fibre Channel Serial Bus dalapvio01

U5791.001.91800WT-P2 19 C09 Empty slot

U5791.001.91800WT-P2 19 C10 Other Communications Device

U5791.001.91800WT-P2 20 C01 PCI 1Gbps Ethernet dalapvio01

U5791.001.91800WT-P2 20 C02 PCI 10/100Mbps Ethernet w/ IPSec dalapvio01

U5791.001.91800WT-P2 20 C03 PCI 10/100Mbps Ethernet w/ IPSec dalapvio01

U5791.001.91800WT-P2 20 C04 PCI 10/100Mbps Ethernet w/ IPSec dalapvio01

U5791.001.91800WT-P2 21 T5 SCSI bus controller dalapvio01

U5791.001.91800WT-P2 21 C05 PCI 1Gbps Ethernet dalapvio01

U5791.001.91800WT-P2 21 C06 Fibre Channel Serial Bus dalapvio01

U5791.001.91800WT-P2 21 C07 Empty slot

U5791.001.91800WW-P1 10 T6 SCSI bus controller dalapvio02

U5791.001.91800WW-P1 10 C08 Fibre Channel Serial Bus dalpocdb01

U5791.001.91800WW-P1 10 C09 Empty slot

U5791.001.91800WW-P1 10 C10 Storage controller dalapvio01

U5791.001.91800WW-P1 11 C01 PCI 1Gbps Ethernet dalapvio02

U5791.001.91800WW-P1 11 C02 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WW-P1 11 C03 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WW-P1 11 C04 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WW-P1 12 T5 SCSI bus controller dalapvio02

U5791.001.91800WW-P1 12 C05 PCI 1Gbps Ethernet dalapvio02

U5791.001.91800WW-P1 12 C06 Fibre Channel Serial Bus dalapvio02

U5791.001.91800WW-P1 12 C07 Empty slot

U5791.001.91800WW-P2 16 T6 SCSI bus controller dalapvio02

U5791.001.91800WW-P2 16 C08 Fibre Channel Serial Bus dalapvio02

U5791.001.91800WW-P2 16 C09 Empty slot

U5791.001.91800WW-P2 16 C10 Other Communications Device

U5791.001.91800WW-P2 17 C01 PCI 1Gbps Ethernet dalapvio02

U5791.001.91800WW-P2 17 C02 PCI 10/100Mbps Ethernet w/ IPSec dalapvio02

U5791.001.91800WW-P2 17 C03 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WW-P2 17 C04 PCI 10/100Mbps Ethernet w/ IPSec dalapvio02

U5791.001.91800WW-P2 18 T5 SCSI bus controller dalapvio02

U5791.001.91800WW-P2 18 C05 PCI 1Gbps Ethernet dalapvio02

U5791.001.91800WW-P2 18 C06 Fibre Channel Serial Bus dalapvio02

U5791.001.91800WW-P2 18 C07 Empty slot

U5791.001.91800WT-P1 13 T6 SCSI bus controller dalapvio01

U5791.001.91800WT-P1 13 C08 Fibre Channel Serial Bus dalpocdb01

U5791.001.91800WT-P1 13 C09 Empty slot

U5791.001.91800WT-P1 13 C10 Empty slot

U5791.001.91800WT-P1 14 C01 PCI 1Gbps Ethernet dalapvio01

U5791.001.91800WT-P1 14 C02 PCI 10/100Mbps Ethernet w/ IPSec dalapvio02

U5791.001.91800WT-P1 14 C03 PCI 10/100Mbps Ethernet w/ IPSec dalapvio01

U5791.001.91800WT-P1 14 C04 PCI 10/100Mbps Ethernet w/ IPSec dalapvio02

U5791.001.91800WT-P1 15 T5 SCSI bus controller dalapvio01

U5791.001.91800WT-P1 15 C05 PCI 1Gbps Ethernet dalapvio01

U5791.001.91800WT-P1 15 C06 Fibre Channel Serial Bus dalapvio01

U5791.001.91800WT-P1 15 C07 Empty slot

U5791.001.91800WT-P2 19 T6 SCSI bus controller dalapvio01

U5791.001.91800WT-P2 19 C08 Fibre Channel Serial Bus dalapvio01

U5791.001.91800WT-P2 19 C09 Empty slot

U5791.001.91800WT-P2 19 C10 Other Communications Device

U5791.001.91800WT-P2 20 C01 PCI 1Gbps Ethernet dalapvio01

U5791.001.91800WT-P2 20 C02 PCI 10/100Mbps Ethernet w/ IPSec dalapvio01

U5791.001.91800WT-P2 20 C03 PCI 10/100Mbps Ethernet w/ IPSec dalapvio01

U5791.001.91800WT-P2 20 C04 PCI 10/100Mbps Ethernet w/ IPSec dalapvio01

U5791.001.91800WT-P2 21 T5 SCSI bus controller dalapvio01

U5791.001.91800WT-P2 21 C05 PCI 1Gbps Ethernet dalapvio01

U5791.001.91800WT-P2 21 C06 Fibre Channel Serial Bus dalapvio01

U5791.001.91800WT-P2 21 C07 Empty slot

U5791.001.91800WW-P1 10 T6 SCSI bus controller dalapvio02

U5791.001.91800WW-P1 10 C08 Fibre Channel Serial Bus dalpocdb01

U5791.001.91800WW-P1 10 C09 Empty slot

U5791.001.91800WW-P1 10 C10 Storage controller dalapvio01

U5791.001.91800WW-P1 11 C01 PCI 1Gbps Ethernet dalapvio02

U5791.001.91800WW-P1 11 C02 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WW-P1 11 C03 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WW-P1 11 C04 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WW-P1 12 T5 SCSI bus controller dalapvio02

U5791.001.91800WW-P1 12 C05 PCI 1Gbps Ethernet dalapvio02

U5791.001.91800WW-P1 12 C06 Fibre Channel Serial Bus dalapvio02

U5791.001.91800WW-P1 12 C07 Empty slot

U5791.001.91800WW-P2 16 T6 SCSI bus controller dalapvio02

U5791.001.91800WW-P2 16 C08 Fibre Channel Serial Bus dalapvio02

U5791.001.91800WW-P2 16 C09 Empty slot

U5791.001.91800WW-P2 16 C10 Other Communications Device

U5791.001.91800WW-P2 17 C01 PCI 1Gbps Ethernet dalapvio02

U5791.001.91800WW-P2 17 C02 PCI 10/100Mbps Ethernet w/ IPSec dalapvio02

U5791.001.91800WW-P2 17 C03 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WW-P2 17 C04 PCI 10/100Mbps Ethernet w/ IPSec dalapvio02

U5791.001.91800WW-P2 18 T5 SCSI bus controller dalapvio02

U5791.001.91800WW-P2 18 C05 PCI 1Gbps Ethernet dalapvio02

U5791.001.91800WW-P2 18 C06 Fibre Channel Serial Bus dalapvio02

U5791.001.91800WW-P2 18 C07 Empty slot

Server9119590SN51A432C

Drawer Serial Bus Slot Adapter LPAR

U5791.001.91800WR-P1 13 T6 SCSI bus controller dalapvio04

U5791.001.91800WR-P1 13 C08 Fibre Channel Serial Bus dalpocdb02

U5791.001.91800WR-P1 13 C09 Empty slot

U5791.001.91800WR-P1 13 C10 Empty slot

U5791.001.91800WR-P1 14 C01 PCI 1Gbps Ethernet dalapvio04

U5791.001.91800WR-P1 14 C02 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WR-P1 14 C03 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WR-P1 14 C04 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WR-P1 15 T5 SCSI bus controller dalapvio04

U5791.001.91800WR-P1 15 C05 PCI 1Gbps Ethernet dalapvio04

U5791.001.91800WR-P1 15 C06 Fibre Channel Serial Bus dalapvio04

U5791.001.91800WR-P1 15 C07 Empty slot

U5791.001.91800WR-P2 19 T6 SCSI bus controller dalapvio04

U5791.001.91800WR-P2 19 C08 Fibre Channel Serial Bus dalapvio04

U5791.001.91800WR-P2 19 C09 Empty slot

U5791.001.91800WR-P2 19 C10 Other Communications Device

U5791.001.91800WR-P2 20 C01 PCI 1Gbps Ethernet dalapvio04

U5791.001.91800WR-P2 20 C02 PCI 10/100Mbps Ethernet w/ IPSec

U5791.001.91800WR-P2 20 C03 PCI 10/100Mbps Ethernet w/ IPSec dalapvio04

U5791.001.91800WR-P2 20 C04 PCI 10/100Mbps Ethernet w/ IPSec dalapvio04

U5791.001.91800WR-P2 21 T5 SCSI bus controller dalapvio04

U5791.001.91800WR-P2 21 C05 PCI 1Gbps Ethernet dalapvio04

U5791.001.91800WR-P2 21 C06 Fibre Channel Serial Bus dalapvio04

U5791.001.91800WR-P2 21 C07 Empty slot

U5791.001.91800WY-P1 10 T6 SCSI bus controller dalapvio03

U5791.001.91800WY-P1 10 C08 Fibre Channel Serial Bus dalpocdb02

U5791.001.91800WY-P1 10 C09 Empty slot

U5791.001.91800WY-P1 10 C10 Storage controller dalapvio03

U5791.001.91800WY-P1 11 C01 PCI 1Gbps Ethernet dalapvio03

U5791.001.91800WY-P1 11 C02 PCI 10/100Mbps Ethernet w/ IPSec dalapvio04

U5791.001.91800WY-P1 11 C03 PCI 10/100Mbps Ethernet w/ IPSec dalapvio03

U5791.001.91800WY-P1 11 C04 PCI 10/100Mbps Ethernet w/ IPSec dalapvio04

U5791.001.91800WY-P1 12 T5 SCSI bus controller dalapvio03

U5791.001.91800WY-P1 12 C05 PCI 1Gbps Ethernet dalapvio03

U5791.001.91800WY-P1 12 C06 Fibre Channel Serial Bus dalapvio03

U5791.001.91800WY-P1 12 C07 Empty slot

U5791.001.91800WY-P2 16 T6 SCSI bus controller dalapvio03

U5791.001.91800WY-P2 16 C08 Fibre Channel Serial Bus dalapvio03

U5791.001.91800WY-P2 16 C09 Empty slot

U5791.001.91800WY-P2 16 C10 Other Communications Device

U5791.001.91800WY-P2 17 C01 PCI 1Gbps Ethernet dalapvio03

U5791.001.91800WY-P2 17 C02 PCI 10/100Mbps Ethernet w/ IPSec dalapvio03

U5791.001.91800WY-P2 17 C03 PCI 10/100Mbps Ethernet w/ IPSec dalapvio03

U5791.001.91800WY-P2 17 C04 PCI 10/100Mbps Ethernet w/ IPSec dalapvio03

U5791.001.91800WY-P2 18 T5 SCSI bus controller dalapvio03

U5791.001.91800WY-P2 18 C05 PCI 1Gbps Ethernet dalapvio03

U5791.001.91800WY-P2 18 C06 Fibre Channel Serial Bus dalapvio03

U5791.001.91800WY-P2 18 C07 Empty slot

Server9119590SN51A432B

Configuring Virtual Ethernet Adapters

Configuring virtual ethernet adapters for use in Mt Xia's high availability environment requires configuration of multiple server side ethernet adapters as well as multiple client side adapters. Each VIO server will have one server side ethernet adapter that can be shared to all client LPAR's requiring virtual ethernet adapters.

This document describes a standard for establishing virtual ethernet adapters in the VIO Server environment. This standard is specific to the numbering scheme used to identify the VLAN ID's of the virtual ethernet adapters. The VLAN ID number is also referred to in the HMC as the PVID number.

This document assumes there are two VIO servers in the environment and the names of the VIO servers are represented by "*vio0" and "*vio5".

The VLAN ID numbers will be three digit numbers, each digit representing a different aspect of the underlying ethernet adapter.

3 Digit VLAN ID Number
First Digit Second Digit Third Digit

5: Boot/Service
6: Standby
7: Backup
8: Management
9: Intra-Frame 0: Gigabit
5: 10/100
9: Bus 0,2,4,6,8: VIO Server with even numbered hostnames
1,3,5,7,9: VIO Server with odd numberd hostnames

The first digit of the VLAN ID numbers associated with virtual ethernet adapters will be used to represent a variety of adapter purposes. Those purposes include boot, standby, backup, management, and intra-frame communications.

500-599: boot/service
600-699: standby
700-799: backup
800-899: management
900-999: intra-frame

The third digit of the three digit VLAN ID number assigned to virtual ethernet adapters associated with the VIO Server named *vio0 will end with a number between 0 and 4.

Example: 500, 501, 502, 510, 520, 521, ...

The VLAN ID numbers assigned to virtual ethernet adapters associated with the VIO Server named *vio5 will end with an odd number beginning at 5.

Example: 505, 506, 507, 515, 525, 526, ...

The second digit of the three digit VLAN ID sequence will represent the adapter speed, gigabit cards will be represented by 0 thru 4, 10/100 adapters by 5 thru 8, and bus speed adapters by a 9. This digit may be reconfigured as necessary.

Examples:

Adapter Speed
VLAN ID Adapter Type Adapter Speed VIO Server

500 Boot 0 Gigabit *vio0

501 Boot 1 Gigabit *vio0

505 Boot 0 Gigabit *vio5

506 Boot 1 Gigabit *vio5

550 Boot 0 10/100 *vio0

551 Boot 1 10/100 *vio0

555 Boot 0 10/100 *vio5

556 Boot 1 10/100 *vio5

590 Boot 0 Bus *vio0

591 Boot 0 Bus *vio0

595 Boot 0 Bus *vio5

596 Boot 1 Bus *vio5

An LPAR may have multiple adapters of a variety of types, for example an LPAR that provides database services and is a member of an HACMP cluster may have boot, standby, management, backup, and intra-frame virtual adapters as follows:

Gigabit adapter used for boot/service address
Gigabit adapter used for standby address
10/100 backup adapter
10/100 management adapter
2 intra-frame adapters

VIO Server Configuration:
VLAN ID Adapter Type Adapter Speed VIO Server

500 Boot Gigabit *vio0

600 Standby Gigabit *vio0

750 Backup 10/100 *vio0

850 Management 10/100 *vio0

990 Intra-frame Bus *vio0

991 Intra-frame Bus *vio0

505 Boot Gigabit *vio5

605 Standby Gigabit *vio5

755 Backup 10/100 *vio5

855 Management 10/100 *vio5

995 Intra-frame Bus *vio5

996 Intra-frame Bus *vio5

LPAR VLAN ID configuration to utilize virtual adapters:
VLAN ID Adapter Type Adapter Speed VIO Server

500 Boot Gigabit *vio0

505 Boot Gigabit *vio5

600 Standby Gigabit *vio0

605 Standby Gigabit *vio5

750 Backup 10/100 *vio0

755 Backup 10/100 *vio5

850 Management 10/100 *vio0

855 Management 10/100 *vio5

990 Intra-frame Bus *vio0

991 Intra-frame Bus *vio0

995 Intra-frame Bus *vio5

996 Intra-frame Bus *vio5

This virtual ethernet information can be automatically gathered from an existing frame through the HMC using the script "virtualeth.ksh. Example output from this script follows:

Server9119590SN51A432B

Adapter Type Slot Trunk Device Port Virtual LAN ID MAC Address LPAR Name

server 10 1 595 12F3F000200A dalapvio01

server 20 1 593 12F3F0002014 dalapvio01

server 15 1 594 12F3F000300F dalapvio02

server 25 1 592 12F3F0003019 dalapvio02

client 10 0 595 12F3F000500A dalpocap01

client 15 0 594 12F3F000500F dalpocap01

client 20 0 593 12F3F0005014 dalpocap01

client 25 0 592 12F3F0005019 dalpocap01

client 10 0 595 12F3F000600A dalpocap02

client 15 0 594 12F3F000600F dalpocap02

client 20 0 593 12F3F0006014 dalpocap02

client 25 0 592 12F3F0006019 dalpocap02

client 10 0 595 12F3F000700A dalpocap03

client 15 0 594 12F3F000700F dalpocap03

client 20 0 593 12F3F0007014 dalpocap03

client 25 0 592 12F3F0007019 dalpocap03

client 10 0 595 12F3F000400A dalpocdb01

client 15 0 594 12F3F000400F dalpocdb01

client 20 0 593 12F3F0004014 dalpocdb01

client 25 0 592 12F3F0004019 dalpocdb01

Server9119590SN51A432C

Adapter Type Slot Trunk Device Port Virtual LAN ID MAC Address LPAR Name

client 520 0 520 EE9530001208 dalapplm73

client 525 0 525 EE953000120D dalapplm73

server 10 1 510 EE953000300A dalapvio03

server 20 1 520 EE9530003014 dalapvio03

server 15 1 515 EE953000400F dalapvio04

server 25 1 525 EE9530004019 dalapvio04

client 10 0 510 EE953000500A dalpocdb02

client 15 0 515 EE953000500F dalpocdb02

client 20 0 520 EE9530005014 dalpocdb02

client 25 0 525 EE9530005019 dalpocdb02

Configuring Virtual SCSI Adapters

Configuration of the virtual I/O adapters requires the knowledge of disk layouts as well as networking configuration. The virtual SCSI adapters require server and client side adapters to be configured on the HMC. The server side portion of the SCSI adapter, configured on the VIO, requires a frame wide unique "slot number" be defined. For high availability a server side portion of the SCSI adapter must be configured for each VIO server. This means that each virtual disk or logical volume connection is associated with two server side SCSI adapters, one on each VIO server. By convention the standard has become that each SCSI adapter is numbered as a multiple of 10, with the first SCSI adapter of the server side high availability pair being configured on the first VIO server and ending with the number 0, i.e., 210, 220, 230, 240, ... The second SCSI adapter of the server side high availability pair is configured on the second VIO server and ends with the number 5, i.e., 215, 225, 235, 245, ...

For each LPAR that uses virtual disk or logical volumes, a client side virtual SCSI adapter must be configured on the HMC. The client side of the virtual SCSI adapter requires additional information and it's settings to correspond with the server side of the SCSI adapter. Coordination of the slot numbers defined here will make debugging and tracking of problems much easier and is highly desired. The information required to configure a client side SCSI adapter includes slot number, the name of the server side SCSI adapter remote partition, and the slot number of the server side SCSI adapter on the remote partition. The client side slot number should correspond with the server side slot number to make debugging and tracking easier. As an example of defining both server and client side SCSI adapters in a high availability environment:

For each LPAR, a pair of virtual SCSI adapters shall be configured to be used for attachment of the operating system and paging disks. Another pair of virtual SCSI adapters shall be configured for the purpose of application disk attachment. The virtual SCSI adapters designated for use as operating system disk attachment shall be numbered between 10 and 199. The virtual SCSI adapters designated for use as application disk attachment shall be numbered between 200 and 499.

Using this standard, each VIO server will have one virtual SCSI adapter per LPAR for the operating system, and one virtual SCSI adapter per LPAR for the application storage. Each LPAR will reference two virtual SCSI adapters, one from each VIO server, for the operating system storage, and two virtual SCSI adapters, one from each VIO server, for the application storage. Examples of this is shown below.

Example Virtual SCSI Slot Numbers
LPAR VIO 0
OS Slot VIO 1
OS Slot VIO 0
Appl Slot VIO 1
Appl Slot

daladcal01 10 15 200 205

daladfim03 20 25 210 215

daladesp01 30 35 220 225

dalapega01 40 45 230 235

dalaaora02 50 55 240 245

Each virtual SCSI adapter may have one or more disks with it, depending upon the LPAR requirements. These disk associations are performed on the VIO server by referencing the slot numbers assigned to each LPAR.

This virtual SCSI adapter information can be automatically gathered from an existing frame through the HMC using the script "virtualscsi.ksh. Example output from this script follows:

Server9119590SN51A432B

Adapter Type Slot Remote LPAR Remote Slot Backing Device LPAR Name

server 100 any 0x8100000000000000//ap01rootlv dalapvio01

server 110 any 0x8100000000000000//ap02rootlv dalapvio01

server 120 any 0x8100000000000000//ap03rootlv dalapvio01

server 130 any 0x8100000000000000//db01rootlv dalapvio01

server 150 any 0x8100000000000000/U5791.001.91800WT-P1-C06-T1-W50060E8003334713-L1000000000000/hdisk5 dalapvio01

server 160 any 0x8100000000000000/U5791.001.91800WT-P1-C06-T1-W50060E8003334713-L2000000000000/hdisk6 dalapvio01

server 170 any 0x8100000000000000/U5791.001.91800WT-P1-C06-T1-W50060E8003334713-L3000000000000/hdisk7 dalapvio01

client 190 dalapvio01 190 none dalpocdb01

server 30 any 0x8100000000000000//pocap01lv dalapvio01

server 40 any 0x8100000000000000//pocap02lv dalapvio01

server 50 any 0x8100000000000000//pocap03lv dalapvio01

server 60 any 0x8100000000000000//pocdb01lv dalapvio01

server 105 any // dalapvio02

server 115 any // dalapvio02

server 125 any // dalapvio02

server 135 any // dalapvio02

server 155 any 0x8100000000000000/U5791.001.91800WW-P1-C06-T1-W50060E8003334703-L1000000000000/hdisk5 dalapvio02

server 165 any 0x8100000000000000/U5791.001.91800WW-P1-C06-T1-W50060E8003334703-L2000000000000/hdisk6 dalapvio02

server 175 any 0x8100000000000000/U5791.001.91800WW-P1-C06-T1-W50060E8003334703-L3000000000000/hdisk7 dalapvio02

client 195 dalapvio02 195 none dalpocdb01

server 35 any 0x8100000000000000//pocap01lv dalapvio02

server 45 any 0x8100000000000000//pocap02lv dalapvio02

server 55 any 0x8100000000000000//pocap03lv dalapvio02

server 65 any 0x8100000000000000//pocdb01lv dalapvio02

client 2 dalapvio01 60 none dalpocdb01

client 3 dalapvio02 65 none dalpocdb01

client 4 dalapvio01 130 none dalpocdb01

client 5 dalapvio01 170 none dalpocap03

client 6 dalapvio02 175 none dalpocap03

client 2 dalapvio01 60 none dalpocdb01

client 3 dalapvio02 65 none dalpocdb01

client 4 dalapvio01 130 none dalpocdb01

client 5 dalapvio01 170 none dalpocap03

client 6 dalapvio02 175 none dalpocap03

client 2 dalapvio01 60 none dalpocdb01

client 3 dalapvio02 65 none dalpocdb01

client 4 dalapvio01 130 none dalpocdb01

client 5 dalapvio01 170 none dalpocap03

client 6 dalapvio02 175 none dalpocap03

client 190 dalapvio01 190 none dalpocdb01

client 195 dalapvio02 195 none dalpocdb01

client 2 dalapvio01 60 none dalpocdb01

client 3 dalapvio02 65 none dalpocdb01

client 4 dalapvio01 130 none dalpocdb01

Server9119590SN51A432C

Adapter Type Slot Remote LPAR Remote Slot Backing Device LPAR Name

server 140 any 0x8100000000000000//s32Cplmrootlv dalapvio03

server 145 any 0x8100000000000000//i32Cplmrootlv dalapvio04

server 130 any 0x8100000000000000//sdb02rootlv dalapvio03

server 140 any 0x8100000000000000//s32Cplmrootlv dalapvio03

client 190 dalapvio03 190 none dalpocdb02

server 145 any 0x8100000000000000//i32Cplmrootlv dalapvio04

client 195 dalapvio04 195 none dalpocdb02

server 65 any 0x8100000000000000//db02rootlv dalapvio04

client 190 dalapvio03 190 none dalpocdb02

client 195 dalapvio04 195 none dalpocdb02

client 2 dalapvio04 65 none dalpocdb02

client 3 dalapvio03 130 none dalpocdb02

Standards

Policies
Guidelines
Procedures
Config VEthnet
Config VSCSI

FREE Domain Registration
included with Web Site Hosting
Tools, Social Networking, Blog
www.siteox.com

Business Web Site Hosting
$3.99 / month includes Tools,
Shopping Cart, Site Builder
www.siteox.com

*AIX^tm^mtXIA*	Site Guide \| Contact Us Mt Xia: *Technical Consulting Group*
	Business Continuity / Disaster Recovery / High Availability Data Center Automation / Audit Response / Audit Compliance


	Home About Mt Xia Mt Xia Officers Privacy Policies FAQs Contact Us Events Press Releases Business Continuity Business Continuity Planning BC Auditing BC Policies BC Guidelines BC Standards BC Procedures BC Automated Deployment Disaster Recovery Disaster Recovery Planning DR Plan Template DR Project Implementation DR Auditing DR Automated Deployment High Availability High Availability Planning HA Policies HA Guidelines HA Standards HA Procedures HA Automated Deployment Tech Support/Training AIX 4.3 Tech Support AIX 5.1 Tech Support AIX 5.2 Tech Support AIX 5.3 Tech Support HACMP 4.4.1 Tech Support HACMP 5.2 Tech Support HACMP 5.3 Tech Support Disaster Recovery Unix / Linux Shell Programming E-Business Downloads Scripts Editors Documentation Standards Project Template E-Business Methodology E-Business Model Random Fortune Cookie